Technotools/Technotools (Chestnut CD-ROM)(1993).ISO/misc_pto/managr09/manager.doc

Text File | 1992-01-31 | 26KB | 483 lines

                           NOTES ON MANAGER.COM 2.09

                                 Matt Roberts
                               5 Cedar St., # 8
                           Montpelier, Vt 05602-3006
                                 [phone]

                                   12-6-91

───────────────────────────────────────────────────────────────────────────────

Note: The Manager was formerly the ASIC File Manager.  I've renamed it because
the term file manager doesn't really describe what I want it to do.  As time
goes by, I expect it to offer a number of features unrelated to files, such as
(hopefully) a calculator, an ASCII chart, the ability to send codes to the
printer (for italic, underline, bold, and whatnot) and all sorts of goodies
that don't have that much to do with files.


                                     BUGS

This section is reserved for bugs in the program.  The main thing that's
nagging me at the moment is in the File-listing utility; subdirectories aren't
labelled as such.  As a result, any file you see in the list could
theoretically be either a user file or a directory.  I've tried everything I
could think of, to no avail.  Looking at the document, I've reached to the
conclusion that I'll be able to solve the problem when and if I learn how to
access machine code from ASIC.  Unfortunately, this isn't likely to happen for
quite a while.  Since I need to fix this to use other parts of the program
more effectively, however, I'll be puzzling over it and I'll try to solve that
problem as soon as I can.

Another problem seems to be in the "Run Other Programs" routine.  Please see
that section for a full descriptions but, in short, some programs won't run
properly with that feature.  I'm going to try to fix it, but I'm not certain
it's something I can do anything about.  We'll find out soon enough, though.

Because of the way I "organize" my work, some of the capabilities of version
2.00 may not yet be documented.  I try to write them in so they're not too
difficult to understand, so you should be able to use them even if they're not
in here.  If that's not so, give me a call and I'll help you through as best I
can.

Finally, not all the error-handling routines have been written yet.  As a
result, you may be informed that the action has been carried out, even if it
hasn't.  If you ask The Manager to remove a directory, and that directory is
not empty (for instance), The Manager will return an error to the program.
Since there's nothing to deal with that error, it will go on to the next step,
which is to tell you that the directory has been removed, even though a
directory can't be removed if it has anything in it.  This will be corrected
in the future, but for now you're temporarily on your own as to checking for
correctly spelled pathnames, etc.  You might want to try creating errors in
certain options that don't always work quite right, to see if the error
routines have been plugged in yet.  I apologize for the hassle, and thank you
for your patience.


                         SYSTEM REQUIREMENTS AND NOTES

The Manager was written using ASIC 3.01 by David Visti.  I find it excellent
2
for most purposes, and recommend it highly.  The author can be reached at P.O.
Box 2952, Raleigh, NC 27602-2952.  Registration is only $10.00, and I sent in
mine before the guy comes to his senses and starts charging what it's worth.

The computer used was an Amstrad PC1512 SD.  This system has an 8086
processor, running at 8MHz (non-switchable).  It has 640K RAM, and 2Mb EMS.
The monitor/display card is a black and white composite monochrome/CGA.  It
has two 5.25", 360K floppy drives, and a 49Mb hard drive card.  1Mb of EMS has
been used to create an EMS disk (same as a RAM disk, but uses EMS).  The
Amstrad PC1512 has been discontinued.

You'll need approximately 130K of RAM to run The Manager.  It was
written under MS-DOS 3.20, but I suspect it will run under lower versions.  I
expect to be doing some testing in the future; I'll let you know whatever I
find out.  You'll also need the two files MANAGER.COM and SEEFILES.COM.  The
file-listing utility is in a separate file because it was the only way I could
fix a bug.  When it was part of the main program, shelling to DOS would result
in the file-listing utility being somehow corrupted.  I tried everything I
could think of, and finally decided that maybe if it was called from DOS
itself, the DOS shell wouldn't bother it.  Worked out fine, though I don't
know why (I make a lot of lucky guesses).  There are a couple of other files
you'll need, but I'll just make a complete list following:

AUTOEXEC.EXE
CONFIG.EXE
MANAGER.COM
SEEFILES.COM

The Manager is primarily a mental exercise, although my ultimate goal is to
offer a program that can do just about everything you can do from DOS.  At the
moment, there are serious limitations, but there are also a few options that
are awfully handy to have, some of which aren't available from the DOS prompt
(as far as I know), and some which do the job in a friendlier or (once in a
great while) better way.  So, there's some solid value here, in my opinion.
If you agree, you're invited to send a $5.00 donation.  If you disagree,
you're still invited, although I suppose you won't be much inclined to accept
(sigh).

The Manager doesn't have a very comprehensive selection of features at
present.  Since ASIC 2.00 and above has the ability to access machine
interrupts, more features can probably be developed, but I don't know how to
write machine code.  As a result, you may find this program a bit
disappointing.  However, it does have some uses, and certainly serves as a
demonstration of how to program with ASIC, since the source code is included.

For some reason, I've become addicted to file managers.  I've already written
one for Locomotive BASIC 2 version 1.16, and I'm currently working on one for
GW-BASIC 3.22.  I'll also be writing a file manager for ApBASIC 1.7 at some
point in the near future, and possibly one using Powerbatch, a standard batch
file, and a compiled batch file.  Maybe one of the reasons I like writing file
managers is the amount I learn about the language, its capabilities and its
limitations.  Anyway, I may be offering others soon.

If you're having trouble using any of the programs on the disk, and the
documentation doesn't seem to help, you can call me between 9AM and 9PM EST,
and I'll do what I can to help.  I'm in and out during the day, so keep
trying.

In the program menu, you'll see selections that might look something like
this:

3
Alt-Fn- Selection.

To get that selection, you'll hold down the Alt key and, while still holding
the Alt key down, press the function key (or other key) indicated by Fn.  So,
if you see

Alt-F1- Do Your Laundry.

hold down the Alt key, and press the F1 key without letting go of Alt, and the
computer will do your laundry.  You may see another menu, from which you would
choose from such options as bleach, fabric softener, and the like.  Maybe my
friends are right; maybe I should get that brain scan after all.


                               USING THE PROGRAM

You start by putting your disk in the drive and typing MANAGER at the DOS
prompt.  After a bit of foolishness, you get to the main options menu, which
invites you to delete files, make a directory, rename files, read today's date
and/or time, shell to DOS, blank your screen, quit, and a bunch of other neat
stuff you can't possibly live without.  You press the function key
corresponding to your choice, or the Esc key to return to DOS, and you're on
your way.  Isn't this exciting?  OK, so I'm easily amused.


                              LISTING DISK FILES

Operation is fairly simple; you just type in the directory in which you want
to view the files, giving the full DOS path.  The concept of a path is fairly
simple, and will be in your DOS manual.  If you don't get it the first time,
don't think you're a dummy; DOS manuals are written by Martians because the
labor is cheap.  Unfortunately, the little green guys haven't quite mastered
the art of English yet, and tend to make simple explanations a bit
complicated.  If you just can't figure out what a path is, give me a call and
I'll see what I can do to help.  Please have your DOS manual ready, and have
your telephone as near to the computer as possible, since it'll help if I can
run you through some simple exercises which involve making directories and
changing to them.  I'd appreciate it, though, if you'd give the DOS manual a
try first, and maybe your computer's technical support line second.  Thanks.

Anyway, once you've typed in the path and directory, you'll be treated to a
list of files.  This list will include directories, but I haven't figured out
a way to label them as such when they're printed on the screen.  I'm working
on it, though.  At the end of the list, you'll be invited to list some more
files; if you respond positively, you'll get to type in your path/directory
again.  Otherwise, you'll go back to the menu.

One important note: if you want to view the root directory of a drive, don't
type the backslash (\).  For instance, to view the files in the root directory
of drive A, you would type A: as your directory.  The backslash will be
supplied by The Manager.


                                DELETING FILES

This is fairly simple, and rather dangerous.  You're warned about the
possibility of losing files, and the impossibility of restoring them, and then
given the opportunity to quit.  If you decline this invitation, you're asked
which file you want obliterated.  You'll input the file you want decimated,
including the drive and path.  You are then warned again  (annoying, ain't
4
I?), and once again given the opportunity to get out of harm's way.  Pressing
any key except Esc will destroy the irreplaceable data in your chosen file.
You are next informed that the foregoing has occurred, and invited to make the
same mistake with a different file.  You really should make backups, you know.


                              MAKING A DIRECTORY

Again, fairly simple.  This time, completely harmless.  The only limitation is
that each directory used takes up some disk space.  It is theoretically
possible to create so many directories you don't have room for any files.

You'll tell The Manager the directory you want created, including drive and
path.  You'll then be informed that the directory you wanted has been
delivered, and be given the opportunity to make another.


                                RENAMING FILES

Have I mentioned that it's a good idea to make backups of all your files?
Here's another good reason.  Certain file extensions cannot be changed without
rendering them useless for their original purposes.  Files with an extension
of .BAT, .COM, .EXE, and other files shouldn't be messed with, unless you know
what you're doing.  Also, some programs use overlay files, and will not run if
they can't find what they're looking for.  Others read and write files with
specific extensions, and won't load them if they've been changed.

On the other hand, you can do almost anything you want (assuming it's legal,
moral, and physically possible) with a backup file.  The original is safe and
sound, and can replace the object of your experiments if things don't work out
as planned.  In fact, you might want some extra security by making a copy of
the copy, and keeping each "version" in a different location.  That way,
whatever befalls one won't be as likely to befall the others.

But I digress (constantly).  You'll first tell The Manager the name of the
file you want to change, including drive and path.  When prompted, you type in
the new name for the old file (if you write down both the old and new
filenames at this point, you can change them back if needful).  The Manager
does the dirty deed, and offers more of the same kind of fun.

You can't change a name across drives.  For instance, you can't change
A:\TEST.DOC to B:\TEST.DOC.  Also, you'll need to use a full path for both the
original file and its new name.  As an example, if you want to change
A:\TEST.DOC to A:\TEST2.DOC, you'll need to specify A:\TEST2.DOC as the new
name.  You can't leave out the drive specifier, and you need to specify any
subdirectories A:\TEST.DOC might be in as well.


                             GETTING THE DATE/TIME

Here you get the option of choosing to get just the date, just the time, or
both.  First you choose to Get Time/Date from the Main Menu, and then choose
which combination from another menu.  As you may have noticed, I like menus.
If the time and/or date on your computer haven't been set properly, you won't
get an accurate reading.  Assuming, however, that everything's the way it
ought to be, you should get what you're looking for (or a reasonable facsimile
thereof).

                                SHELLING TO DOS

5
You press the key for the DOS shell.  You are prompted for the drive where
COMMAND.COM can be found.  You type in the letter, but not a colon (:).  You
are told to use the DOS command EXIT to return to The Manager.  You do all the
things I wish you could do with this program.  You type EXIT.  You see the
menu.  Are you having fun yet?


                             BLANKING YOUR SCREEN

If you press the key for this feature, your screen will go dark.  This will
help save your screen from burning "holes" (places where nothing can be
printed) on your monitor.  To return to the Options Menu, press any key.


                         CHECKING FOR A GRAPHICS CARD

Does exactly what it says.  Checks for a graphics card, and tells you one way
or the other.  I don't know if it will recognize MGA (A.K.A. Hercules), but I
kind of doubt it.  If I get a chance to test it, I'll let you know.


                          CHANGING TO 40-COLUMN MODE

I designed this feature to make it possible for the visually impaired to use
The Manager.  I assume the larger text makes it easier to read, but I don't
really know.  If you're visually impaired, and have suggestions on how to make
the screen writes more legible, I'd appreciate hearing from you.  I'm pretty
sure you need a graphics card to access this wider print mode.  I'll check
that out as soon as I can, but it may not be for a long time.

There are certain options you can use from the 80-column mode that you can't
use from 40-columns.  For instance, since you need a graphics adapter (I
think) in order to get 40-column width, I figured it was silly to offer the
option that checks for a graphics adapter.  The file-reading option won't work
properly, since the file won't print properly on the screen.  Vern Buerg's
LIST.COM can deal with 40-column mode, because it reads the file into memory
where you can use the arrow keys to scroll sideways.  Unfortunately, I don't
have the skill to write a program that can do the same.  It's a goal of mine
to be able to do precisely that, but I think it'll be quite a while before I
figure out how to do it.  As soon as I do, though, I'll include it.  Anyway,
if you don't see an option in 40-column mode, it's probably because I couldn't
figure out how to write it so it would run properly, or because it wouldn't
make sense to offer it in the first place.  I'm the only one who can do much
about the former, but the latter is always open to discussion.  I don't
guarantee you'll convert me, but it won't do me any harm to listen to your
opinions.  So, opine to your heart's content, at the address on the first
page.


                                READING A FILE

This feature allows you to read a file on your screen.  It's very primitive,
and is essentially an extension of the DOS command TYPE and the DOS command
MORE.  The text file scrolls past your screen.  It'll stop at each screenful,
and invite you to press a key to continue.  You can also stop the scrolling by
pressing the space bar.


                                PRINTING A FILE

6
This one is like the file-reading routine, except you're printing (surprise).
You press the space bar to pause printing.  There will still be data in the
printer's buffer, and I don't know a way to flush that without losing the
place in the file, so you'll have to take the system off-line if you need to
stop in a hurry.  If you're not in a rush, though, it'll stop printing when
the data in its buffer is printed.  Press any key to continue printing.  When
you press the space bar to pause, there will probably be a few seconds delay
before it can process the keypress.  That's because it processes the text file
one line at a time, and it can't get to processing your keypress until it's
finished with the line it's working on.  It won't increase the amount printed,
except by that one line.  Don't press the space bar again, because The Manager
will process both keypresses, in order, and will assume you want to continue
printing.

You can quit printing by pressing the Esc key.  Again, it will probably take a
second or two for The Manager to finish with the line it was working at the
time, and get to your keypress.  The amount printed will only be increased by
that one line, and you'll be sent back to the menu shortly.  If you press Esc
twice, The Manager will process both Esc key presses, first sending you back
to the menu, and then sending you back to DOS.


                            RUNNING OTHER PROGRAMS

With this feature, you first type in the name of the program you want to run,
including the drive and path.  For instance, if you want to run LIST.COM,
which is on drive C: in the UTILITY directory, you would type

                              C:\UTILITY\LIST.COM

at the prompt.  You'll then be prompted for a parameter, which in this case
will be the name of a file you want to view.  When finished, you'll be asked
to press a key.  This is so you can still see the last screen of whatever the
program was doing.  Once you press a key, the screen will clear, and you'll be
offered the chance to run another program.  If you accept, you'll get to do
the same thing over again; otherwise, you'll be sent back to the main menu.

A few notes:  I could have sworn I'd tested this feature, and it basically
worked.  But a few days ago, I checked it out, and I had to replace some
screwed-up code.  All I can figure is I must have screwed up this section
somehow when I was trying to work on some other area, or moved/copied some
text, or modified part of a routine so it was a subroutine (I've done all of
those lately).  Anyway, I added some code, deleted some code, tested some
code, swore a few times, and now I think this section works about as well as
it's going to.  Unfortunately, that isn't as well as I'd prefer.

Apparently, three of my command-line parameters (/l, /L, and /40) get sent
along with the CALL command.  I can't for the life of me figure out why but,
as a result, programs like CHKDSK just won't run.  I've got some ideas for an
error routine that might fix that, but it might not either and it'll be a
little while before I get to it.  Until then, we'll all have to be frustrated.
I send copies of this disk to Mr. Visti each time I upgrade my registration
for ASIC, so when version 4.0 comes out he'll have an opportunity to find out
about this.  From the replies I've gotten, he does check the disk out for the
purpose of finding potential bugs in the compiler or unclear areas in his
documentation.  So, if it's a problem with the compiler, it'll likely be fixed
in the future.


                                  PARAMETERS

7
Using parameters from the DOS prompt can save you time, bypassing the intro
screens, taking you directly to the module where the work you want to do
resides and, for simple jobs, doing that bit of work automatically.  You can
see a list from the menu, which looks remarkably similar to the one listed
following.  Here's the list of the parameters you can currently use.

Typing MANAGER /? will let you view screens which contain this same
information.  The command for 40-column mode is MANAGER /40 ?

Typing MANAGER /S will supposedly let you see a list of disk files.  To list
files with the wide text option, type MANAGER /40 S.

Typing MANAGER /D lets you delete files.  Make backups.  The 40-column
version is MANAGER /40 D.

Typing MANAGER /M moves you to the directory-making module.  In 40-columns,
MANAGER /40 M.

Typing MANAGER /N moves you to the module for renaming files.  Make backups.
40-column users, type MANAGER /40 N.

Typing MANAGER /G lets you view the time and/or date.  MANAGER /40 G in 40-
column mode.

Typing MANAGER /B lets you blank your screen.  MANAGER /40 B in 40-column
width.

Typing MANAGER /P lets you check for a graphics adapter.

Typing MANAGER /V will let you use the file-reading feature.

Typing MANAGER /L calls the file-printing routine.  For 40-column users, the
command is MANAGER /40 L.

Typing MANAGER /40 will put you in 40-column mode, provided you have a
graphics adapter, and give you the 40-column menu.


In each case, either upper- or lower-case should be fine.  If it isn't, I
goofed, and I'd appreciate it if you'd let me know so I can ungoof.  Thanks.


                             WRITE-PROTECTED DISKS

If you try to delete files, make directories, or rename files on a disk that's
write-protected, DOS will interrupt The Manager with a Write-Protect Error.
You are given the usual opportunities to Abort, Retry, Ignore.  If you wish,
you can remove the write-protect tape or move the write-protect tab (depending
on your type of disk), or put an unprotected disk in that drive, and try
again.  If you choose Abort, you'll be returned to DOS.  As far as I know, I
have no control over that.  If I figure a way to get out of leaving the
program in case of an Abort, I'll write it into The Manager.

Please bear in mind, should you get that type of error, that a disk is usually
write-protected (whether by you or someone else) for good reason.  I would
advise you to think twice about unprotecting the disk.  Since there are no
restrictions on reading from a protected disk, you might want to consider
making a copy of that disk, and doing what you want on the copy.  That way you
get to manipulate the files to your heart's content, without damaging the
protected disk.


8
                                ERROR ROUTINES

There are a number of error routines in The Manager in case you should attempt
to do something either the program or DOS can't do.  I've designed these so
that, should you start typing in a correction and then decide to quit, you can
press Esc at any time.  It was a little on the tricky side for me to code; I
spent a long time testing, but I may not have caught all the bugs.  As always,
let me know if I missed anything.



                                 IN CONCLUSION

ASIC is still being modified, and I expect more features to be available to
such cement-headed programmers as myself.  When this occurs, MANAGER.COM will
undoubtedly flesh out a bit.  You shouldn't think of this program as
representative of ASIC's capabilities; I've written a number of utilities, for
instance, which saved me the price of the registration many times over.  In
addition, I'm still a novice programmer, though I expect to graduate to
beginner some time soon.  More experienced programmers will find the
facilities (BLOAD, PEEK, POKE, etc.) to really make your programs sit up and
take notice.  I don't know how to use any of the advanced commands, so don't
judge the compiler by the programs I've written.

Your comments, questions, and criticisms would be greatly appreciated,
including correcting my grammar, spelling, etc.  My goal is to write quality
software, and I need your help to do it.  Thanks.


                                     TESTS

Version numbers exist for the purpose of testing this disk's utilities on
other computers.  Version 1.00 has been tested on the following:

Amstrad PC1512 SD: This system has an 8086 CPU, a composite monochrome
monitor, and CGA which can access 16 shades of gray (or color with a color
monitor) with a resolution of up to 640 X 200.  The system originally came
with 512K RAM, which I've upgraded to 640K.  I've also added a 2 Mb EMS card.
It came with a single 5.25", 360K drive.  A second internal drive of the same
type was later added, and I've installed a 49Mb hard disk card.  Operating
system is MS-DOS 3.20.  This line has been discontinued.  The Manager had no
problems running on the Amstrad.


Packard Bell Pack-Mate: This system has an 80286 CPU and a color VGA monitor.
There's 640K RAM, and 384K Extended Memory.  Drives are one 40Mb internal hard
disk, one 5.25", 1.2Mb drive, and one 3.5", 1.44 Mb drive.  Operating system
is MS-DOS 3.30.  FILE-MAN 1.00 had no problems running on the Packard Bell.

Version 2.00 has not been tested on any systems other than the Amstrad, where
it showed no problems.